Composing Non-orthogonal Meta-programs Composing Non-orthogonal Meta-programs

A key feature of meta-level architectures is the strict separation between the application and the non-functional requirements. In a base-level, the application behaviour is modelled. Other requirements are handled in a meta-program. This makes both application and meta-program reusable. We introduce a mechanism based on high-level declarative policies to overcome the diiculty of tailoring a meta-program to application demands, without sacriicing its genericity. These policies can also be used in the composition of multiple meta-programs in a meta-tower. Often, the requirements are not completely orthogonal, and dependencies between the meta-programs in the tower are generated. Through policy speciications, these dependencies can be described separately from the implementation. This results in reusable and composable meta-programs in a more general case. Abstract A key feature of meta-level architectures is the strict separation between the application and the non-functional requirements. In a base-level, the application behaviour is modelled. Other requirements are handled in a meta-program. This makes both application and meta-program reusable. We introduce a mechanism based on high-level declarative policies to overcome the diiculty of tailoring a meta-program to application demands, without sacriicing its genericity. These policies can also be used in the composition of multiple meta-programs in a meta-tower. Often, the requirements are not completely orthogonal, and dependencies between the meta-programs in the tower are generated. Through policy speciications, these dependencies can be described separately from the implementation. This results in reusable and composable meta-programs in a more general case.